APPSEC-60188: gracefully accept null in APIGW response
#960
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I strongly suspect the .NET Lambda SDK (from Amazon) produces `null` values instead of omitting fields, which appears to be accepted by API Gateway but is presently rejected by our parsing logic. This addresses this problem and adds a new test case. JJ-Change-Id: vprmkv
RomainMuller
changed the title
null in APIGW responsenull in APIGW response
astuyve
approved these changes
Dec 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I strongly suspect the .NET Lambda SDK (from Amazon) produces
nullvalues instead of omitting fields, which appears to be accepted by API Gateway but is presently rejected by our parsing logic. This addresses this problem and adds a new test case.JJ-Change-Id: vprmkv
ZD: 2375557
Jira: APPSEC-60188